SMART on FHIR with Okta - Implementation Template

You can deploy the solution to the Anypoint platform.

The following endpoints have been implemented to retrieve Okta API well-known openid-configuration and dynamic client registration:

• /metadata
• /smart-configuration
• /clients

The /clients endpoint is a wrapper for Okta API client registration.

Note: Okta API client registration endpoint (/v1/clients) requires an API token for authorization, whereas Inferno client suite can send only a Bearer token.

/metadata endpoint

• Retrieves the OpenID Connect metadata related to the specified authorization server using Okta /.well-known/openid-configuration.
• Extracts the required endpoints (token_endpoint, authorization_endpoint, introspection_endpoint, revocation_endpoint).
• Constructs the required payload for SMART on FHIR Discovery.

This information can be used by clients to programmatically configure their interactions with Okta. Custom scopes are returned only when they are configured to be publicly discoverable:

/smart-configuration endpoint

• Retrieves OpenID Connect metadata related to the specified authorization server using Okta /.well-known/openid-configuration.
• Constructs the target payload by adding capabilities and custom dynamic client registration wrapper endpoint for SMART on FHIR Discovery:

/clients endpoint

• A wrapper for Okta API client registration.

Note: Okta API client registration endpoint (/v1/clients) requires API token for authorization, whereas Inferno client suite can send only a Bearer token.